Payment service capable of being integrated with merchant sites

ABSTRACT

A computer-implemented service integrates with merchant sites to enable registered users of the service to perform purchase transactions on the merchant sites. In one embodiment, a merchant can incorporate a reference to a display object served by the service into coding of a page of the merchant&#39;s site. When the page is loaded by a user&#39;s browser, the reference causes the browser to request the display object from the service for display on the page. If the user is recognized by the service, the service may return a personalized display object that includes functionality for the user to perform a purchase transaction using the service. Also disclosed are embodiments that enable users to initiate transfers of personal account information to the merchant sites.

PRIORITY CLAIM

This application is a continuation of U.S. application Ser. No.13/436,440, filed Mar. 30, 2012, which is a continuation of U.S.application Ser. No. 13/006,171, filed Jan. 13, 2011 (now U.S. Pat. No.8,160,935), which is a continuation of U.S. application Ser. No.12/357,211, filed Jan. 21, 2009 (now U.S. Pat. No. 7,877,299), which isa continuation of U.S. application Ser. No. 09/457,839, filed Dec. 9,1999 (now U.S. Pat. No. 7,966,259). The disclosures of the aforesaidapplications are hereby incorporated by reference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

This invention relates generally to computer-implemented services forenabling users to conduct purchase transactions on third party merchantsites.

2. Description of the Related Art

Consumers today routinely shop and make purchases of products andservices over the Internet using web browsers. Numerous Internetmerchants have set up web sites allowing customers to browse throughdescriptions of products and services. After the customer has selectedone or more products for purchase, Internet merchants typically providethe customer with a checkout page requesting payment information fromthe customer. The payment information usually comprises a credit cardnumber, expiration date, cardholder name, and any other information thatmay be required to authorize a charge against the customer's card. Ifapplicable, shipping information may also be requested on the checkoutpage.

It is often considered an inconvenience for a customer to have to enterin the often lengthy amount of information required to process a creditcard transaction each time the customer makes a purchase. As aconsequence, a number of merchants allow the customer to select a userID and a password when providing payment and/or delivery information.The merchant catalogs the customer's information and associates it withthe user ID and password. In this manner the customer only needs toenter in her user ID and password in order to make subsequent purchases.Customers typically, however, make purchases from more than onemerchant. Different merchants may have different formats for a user IDand a password. Furthermore, a customer's preferred user ID may alreadybe in use by another customer at a particular merchant. Consequently, acustomer will likely have to remember several user IDs and/or passwords.

Another solution to the inconvenience of filling out lengthy forms,called a wallet or digital wallet, has been suggested. A digital wallettypically comprises a small software layer that functions in conjunctionwith a web browser on the customer's computer. The wallet storescustomer payment and/or delivery information on the customer's computerand provides the information to merchants using a standardized protocolupon the direction of the customer. Many customers, however, considerthe process of downloading, installing, and configuring the walletsoftware too complicated, time consuming or burdensome.

Another advance is the advent by Amazon.com of 1-Click™ shopping. Withthis feature, the user initially specifies a credit card, shippingaddress, shipping method, and/or other default information to be usedfor 1-Click purchases, and can thereafter purchase items with a singlemouse click. The 1-Click feature involves placing an identifying cookieon the customer's computer. The customer's web browser returns thecookie to Amazon.com's web server when the web site is accessed. The webserver can then read the cookie to identify the customer and present tothe customer a web page with the option of purchasing a product with asingle click using the information already on file. Additional detailsof the 1-Click feature are set forth in U.S. Pat. No. 5,960,411, thedisclosure of which is hereby incorporated by reference.

Other solutions (see, e.g. U.S. Pat. Nos. 5,715,314 and 5,815,665)involve the use of a third party payment or brokering service. Thecustomer first registers with the payment or brokering service. Thepayment or brokering service can then authenticate the customer duringsubsequent transactions with merchants. The payment or brokering servicebills the customer for each authorized transaction and provides paymentsto the merchants.

BRIEF DESCRIPTION OF THE DRAWINGS

Referring now to the drawings in which like reference numbers representcorresponding components throughout:

FIG. 1 illustrates the principal components of a preferred embodiment ofa customer authentication and data transfer system;

FIGS. 2A-B are two flowcharts illustrating a general embodiment of thesystem;

FIG. 3 illustrates a data flow diagram showing the transfer ofinformation between a customer, an information service, and a merchantin accordance with the general embodiment of FIGS. 2A-B;

FIGS. 4A-G illustrate a number of example web pages that are displayedto a customer in accordance with a first specific embodiment of thepresent invention;

FIG. 5 is a flowchart illustrating a process through which the systemprovides customer information to a merchant in accordance with the firstspecific embodiment;

FIG. 6 illustrates a data flow diagram showing the transfer ofinformation between the customer, the information service, and themerchant in accordance with the first specific embodiment;

FIGS. 7A-E illustrate a number of example web pages that are displayedto a customer in accordance with a second specific embodiment of thepresent invention;

FIG. 8 is a flowchart illustrating a process through which the systemprovides customer information to a merchant in accordance with thesecond specific embodiment;

FIG. 9 illustrates a data flow diagram showing the transfer ofinformation between the customer, the information service, and themerchant 104 in accordance with the second specific embodiment;

FIGS. 10A-E illustrate a number of example web pages that are displayedto a customer in accordance with a third specific embodiment of thepresent invention;

FIGS. 11A-B are a flowchart illustrating a process through whichcustomer information is provided to a merchant in accordance with thethird specific embodiment; and

FIG. 12 illustrates a data flow diagram showing the transfer ofinformation between the customer, the information service, and themerchant in accordance with the third specific embodiment.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

In the following description, reference is made to the accompanyingdrawings, which show, by way of illustration, specific embodiments inwhich the invention may be practiced. Numerous specific details of theseembodiments are set forth in order to provide a thorough understandingof the present invention. However, it will be obvious to one skilled inthe art that the present invention may be practiced without the specificdetails or with certain alternative components and methods to thosedescribed herein. In other instances, well-known methods, procedures,and components have not been described in detail so as not tounnecessarily obscure aspects of the present invention.

I. System Components

FIG. 1 illustrates the principal components of a preferred embodiment ofa customer authentication and data transfer system 100. A customer 102can be any entity or individual that wishes to make purchases ofproducts or services from a merchant 104. The merchant 104 is preferablyan entity that sells products or services from a merchant web site 106,which is implemented using one or more physical servers 108. In order toselect and purchase products or services, the customer 102 preferablyuses a web browser 109 running on a computer 110. The computer 110 isconnected to the merchant server 108 through a communications network112, which is preferably the Internet.

In order to make purchases, the customer 102 typically provides varioustypes of customer information to merchants 104. The customer informationmay include, for example, the customer's name, shipping address(es),email address, payment information, 1-Click settings, and the names andaddresses of common gift recipients. The customer may also be requiredto provide authentication information, such as a user ID (which may bethe user's email address) and password. The merchant 104 may alsocollect and store various other types of customer information, includingpurchase histories and other data that indicates customers' interests.

The information service 114 is an entity that serves as an intermediaryfor providing customer information to the merchant 104 in a secure andconvenient manner through the communications network 112. The customer102, using the computer 110, interacts with the information service 114through an information service web site 116 that is serviced by aninformation service server 118. The information service server 118prompts the user to enter various types of customer information andauthentication information and stores and associates this information ina database 120. The information service 114, through its server 118 anddatabase 120, authenticates the customer 102 using the authenticationinformation, and electronically provides some or all of the customer'sinformation to the merchant 104 and possibly other merchants. Forpurposes of the following description, the terms “customer information”and “customer's information” will be used to refer primarily toinformation other than the authentication information (user ID andpassword).

In the context of the present disclosure, actions indicated as beingtaken by the customer 102 are preferably performed by or through, asapplicable, the web browser 109 and/or the computer 110. Actionsindicated as being taken by the merchant 104 are preferably performed byor through, as applicable, the merchant server 108 and its associatedsoftware components. Actions indicated as being taken by the informationservice 114 are preferably performed by or through, as applicable, theinformation service server 114 and its associated software components.The computers and servers referenced herein are preferablygeneral-purpose computers, although application-specific hardware couldbe used to perform certain tasks.

In one preferred embodiment, the information service 114 is also anInternet merchant, separate and different from the merchant 104.Accordingly, the information service 114 typically will have availableto it an existing database of customer information acquired as anInternet merchant. Existing customers of the information service 114 (asan Internet merchant) will preferably be able to use the customerauthentication and data transfer system 100, without an additionalregistration, to make purchases from merchants 104 other than theinformation service 114. For example, Amazon.com, acting as aninformation service 114, can provide its customers the option to shopfrom web sites of other merchants (e.g. www.gap.com) using theirAmazon.com user IDs and passwords. Although the information service 114is preferably an Internet merchant, it may alternatively be anon-merchant entity.

II. General Embodiment

A general embodiment of the invention will now be described withreference to FIGS. 2A-B and FIG. 3. This general embodiment is intendedto illustrate the basic operation of the customer authentication anddata transfer system 100. The three following sections will describethree specific embodiments based upon the general embodiment presentedin this section.

A. Methods and Data Flows

FIGS. 2A-B are two flowcharts 200, 220 illustrating the operation of thegeneral embodiment of the system 100. The flowcharts 200, 220 arepresented in a three column format wherein the actions performed by eachof the customer 102, the information service 114, and the merchant 104are depicted in a respective column under the name of the acting entity.The remaining flowcharts in this disclosure also follow the same format.

FIG. 3 illustrates a data flow diagram 300 showing the transfer ofinformation between the customer 102, the information service 114, andthe merchant 104 in accordance with the general embodiment. Informationsent between the customer 102, the information service 114, and themerchant 104 is preferably sent through the computer 110, theinformation service server 118, or the merchant server 108 over thecommunications network 112. In the alternative, the information service114 could communicate with the merchant 104 over a separatecommunications network 112 other than the one used between theinformation service 114 and the customer 102. For example, the transferof customer information from the information provider 114 to themerchant 104 could occur over a direct dial telephone connection.

In steps 202-206 of the flowchart 200 in FIG. 2A a merchant 114registers to use the authentication and data transfer system 100. At afirst step 202, the information service 114 solicits merchants toregister to use the system 100. The solicitation can be accomplishedthrough Internet advertising, e-mail, or any off-line forms ofsolicitation typically used by businesses. At a next step 204, amerchant registers with the information service 114. The registrationcan be performed on-line, through the information service web site 116,or off-line, through conventional means. At step 204, the identity ofthe merchant and its server information are preferably stored in theinformation service's database 120. At a next step 206, the informationservice 114 and the merchant 104 establish a secure communications linkover the communications network 112 through which customer informationand other information can be transferred. Step 206 may involve theinstallation and configuration of software on the merchant server 114.Steps 202-206 are generally depicted in the data flow diagram 300 (FIG.3) by the two-way link 302 between the information service 114 and themerchant 104, titled “Merchant Registration.”

The process of registering merchants as in steps 202-206 is suggestedprimarily to improve the security aspects of the present invention, butis not essential to its operation. By registering the merchant 104, theinformation service 114 can request information sufficient to verifythat the merchant 104 is a valid business concern. In this manner, theinformation service 114 can, by one method, avoid inadvertentlyproviding sensitive information to illegitimate entities. In alternativeembodiments, steps 202-206 could be omitted.

In steps 210-214 of the flowchart 200 a customer 102 registers to usethe authentication and data transfer system 100. In the illustratedexample, steps 202-206 occur before steps 210-214, however, steps210-214 could occur before or at the same time as steps 202-206. At step210, the information service 114 solicits customers to register with theservice and to provide customer information, a user ID, and a password.The solicitation may be accomplished either on-line on the Internet orthrough conventional means. At step 212, the customer 102 registers withthe information service 114 and provides customer information, a userID, and a password. This registration is preferably performed throughthe information service web site 116 and may be performed in conjunctionwith a purchase made from the information service 114. At a next step214, the information service 114 associates and stores the customerinformation, the user ID, and the password in the database 120. Steps210-214 are generally depicted in the data flow diagram 300 by thetwo-way link 304 between the customer 102 and the information service114 titled “Customer Registration.” Many merchants 104 and manycustomers 102 will typically register with the information service 114.

Referring now to the flowchart 220 in FIG. 2B, the customer 102 browsesat the merchant web site 106 and identifies product(s) and/or service(s)for purchase at step 222. The exchange of web pages and selections bythe customer 102 and merchant 104 are indicated by the two-way link 306in the data flow diagram 300. In an alternative embodiment, the customerinformation may be transferred to the merchant 104 without requiring thecustomer 102 to make a purchase. At a next step 224 of the flowchart220, the customer 102 requests (implicitly or explicitly) that theinformation service 114 provide the customer information to the merchant104. The request of step 224 is indicated by the one-way link 308 fromthe customer 102 to the information service 114 in the data flow diagram300. The request 308 results from a particular action by the customer102, such as a clicking on a “transfer information” link on theinformation service web site 116 or a clicking on a “purchase” link onthe merchant web site 106.

At step 226, the information service 114 authenticates the customer 102,preferably by requesting that the customer 102 provide the user ID andpassword. Step 226 is depicted by a larger block that extends above andbelow steps 222 and 224 to emphasize that the authentication step neednot occur at a specific time relative to steps 222 and 224. Althoughother steps are shown throughout the drawings in a particular order, itwill be recognized that the order can be varied in many instances. Theauthentication of step 226 is indicated by the two-way link 310 betweenthe customer 102 and the information service 114 in the data flowdiagram 300. Once steps 224 and 226 have been completed, the informationservice 114 provides some or all of the customer's information to themerchant 104 at step 228. The transfer of the customer information ofstep 228 is indicated by the one-way link 312 from the informationservice 114 to the merchant 104 in the data flow diagram 300. At step230, the merchant 104 receives the transferred customer information andprocesses the transaction.

In the preferred embodiment, the user ID is the e-mail address ofcustomer 102, and the password is a secret code selected by the customer102. The customer information transferred to the merchant preferablyincludes payment and delivery information, such as, for example, acustomer name, a credit card number, a credit card expiration date, abilling address, and a delivery address. The transferred customerinformation may also include, for example, a preferred shipment method,the customer's 1-Click settings, and the names and addresses of giftrecipients. The transferred information may also include the customer'spurchase history (optionally including items purchased from othermerchants) and “interests” profile (specified explicitly by the customeror derived from the customer's activities) and other types ofinformation that may be used by the merchant 104 to generate personalpurchase recommendations or otherwise customize the merchant web site106. In implementations in which the merchants store the transferredinformation for subsequent use, the customer's user ID and password mayalso be transferred, or may be captured by the merchant duringauthentication of the customer.

Further, specific types of customer information provided to a merchantby the information service 114 may be dependent upon the merchant's typeof business. For example, when the customer 102 shops at a web site of asporting goods merchant, the information service 114 may expose to thesporting goods merchant all prior purchases or interests falling withinthe “sports” category. The sporting goods merchant could then use thisinformation to customize the web site for the customer 102. When thecustomer sets up an account with an online stock trading firm, thetransferred customer information may include a social security number ora bank account number.

The information service web site may present the customer an option tospecify or restrict the customer information that is transferred, and/oran option to specify the merchants 102 to which the customer informationis transferred.

B. Security

A number of the transactions involved in the above-described embodimentwould pose security risks if transacted over an insecure communicationslink. Step 212, for example, wherein the customer provides sensitiveinformation is preferably conducted using encryption to provide a secureand private communication link. In the context of the present invention,communications of sensitive information, such as a user ID, a password,or customer information are preferably effectuated over securecommunications links.

A number methods and protocols for providing secure communication linksare presently available and well known in the art. Applicable methodsand protocols include asymmetric key encryption (public-private keyencryption), symmetric key encryption, and SSL (Secure Sockets Layer). Asecure communications link can also be established using a directconnection through a separate or secure communications network, such as,for example, a direct connection between the information service 114 andthe merchant 104.

C. Communications Protocol

In the preferred embodiment, the customer 102, the merchant 104, and theinformation service 114 communicate using the hypertext transferprotocol (hereinafter HTTP). HTTP is the principal protocol that webbrowsers use to communicate with web servers over the Internet. When aweb browser follows a hypertext link on a web page, the browser is saidto generate an HTTP request. Associated with each HTTP request is theuniform resource locator or URL of the hypertext link. The HTTP requestis serviced by a server that handles the URLs within the domain of theserver. As HTTP and its related concepts are well known in the art, theywill not be discussed in further detail herein. It will be noted thatwhile the use of HTTP is suggested in the preferred embodiment, othercommunications protocols could be used.

III. First Specific Embodiment

In a first specific embodiment of the present invention, an Internetmerchant 104 displays a form, preferably on a checkout page on themerchant web site 106, requesting the entry of a customer's user ID andpassword. The Internet merchant 104 then submits the entered user ID andpassword to the information service 114. The information service 114 inturn returns to the merchant 104 the customer information associatedwith the user ID and password, or returns an error message if the userID/password pair is invalid. The merchant then presents to the customer102 an order confirmation page that allows the customer 102 to confirmthe sale. Once the customer 102 has confirmed the sale, the merchant 104uses the customer information to process a payment and, if applicable,ship the order.

In the first subsection below, a set of example web pages illustratesthe present embodiment from the perspective of the customer 102. In anext subsection, a flowchart and data flow diagram illustrate thepresent embodiment from an implementation perspective. In a thirdsubsection, a number of alternative implementations of the embodimentare described.

A. Example Web Pages

FIGS. 4A-G illustrate a number of example web pages that are displayedto a customer 102 in accordance with the first specific embodiment ofthe present invention. In the illustrated example, Merchant.com, ahypothetical merchant, serves as the Internet merchant 104, andAmazonwallet.com serves as the hypothetical information service 114. Inthe context of these web pages, “Amazon Wallet” represents the name of aservice, provided by the present embodiment, that a customer 102 uses tomake purchases from multiple Internet merchants using only a single userID and password set.

FIG. 4A illustrates an Amazon Wallet New User Page of theAmazonwallet.com web site 116. The page has form entry fields for a userID, a password, and customer information such as a shipping address, acontact phone number, and payment information. In the illustratedembodiment, the payment information comprises a credit card number, thecredit card expiration date, the name displayed on the card, and thebilling address of the card. As will be discussed in further detailbelow, the customer's mother's maiden name is also preferably requestedin order to maintain the security of the information submitted. Once anew customer 102 fills in the new user information and submits the form,the customer 102 can then use the wallet to shop at the web sites ofInternet merchants that have registered with the information service114.

If the customer 102 is already an existing customer of Amazon.com, whichoperates Amazonwallet.com in this example, the process of filling in thenew user information may be bypassed. In this case, the customerinformation already on file with Amazon.com could be used to make theAmazon Wallet automatically active.

FIG. 4B illustrates a Checkout Page of the Merchant web site 106 that acustomer 102 reaches after selecting one or more products and/orservices for purchase. The Checkout Page lists the order and presents tothe customer 102 an option to enter payment and possibly deliveryinformation manually or to use the Amazon Wallet. If the customer 102chooses to use the Amazon Wallet, the customer 102 enters her user IDand password and clicks on the associated button.

FIG. 4C illustrates an Order Confirmation Page that is next displayed tothe Amazon Wallet customer 102 on the Merchant.com web site 106. Thepage again lists the order, the name of the customer 102 in order toconfirm the identity of the customer, and displays a “confirm order”button. The Amazon Wallet customer 102 next sees a Thank You page on theMerchant.com web site 106 as illustrated in FIG. 4D. The page confirmsthat the order has been placed, provides an order number for ordertracking, and thanks the customer 102.

FIG. 4E illustrates an Amazonwallet.com Login to Account Access Page ofthe Amazonwallet.com web site 116. This page serves as a gateway to thecustomer's access to her own customer information. In addition to theAmazon Wallet user ID, and password, the page also requests that thecustomer 102 enter her mother's maiden name.

The maiden name of the customer 102 is requested in order to closesecurity loopholes by only requesting the customer ID and password. Asimple example will serve to illustrate one such security loophole.Suppose that only the user ID and customer password were required togain access to the customer information. These two pieces of informationare the same that are requested by other Internet merchants. Suppose anillegitimate entity posing as an Internet merchant posted a web site andpurported to service Amazon Wallet customers 102. The illegitimateentity could solicit Amazon Wallet customers 102 to enter their userIDs, and passwords. Supposing the Amazon Wallet Account Access Page didnot require an additional element of information such as a mother'smaiden name, the illegitimate entity could use the user IDs andpasswords acquired from unsuspecting customers 102 to access and/orchange confidential customer information on the Amazon Wallet web site.By requiring customers 102 to provide an extra element of information togain access to their own information, the danger of this loophole isdrastically reduced. This feature also prevents a registered merchant104 from fraudulently modifying a customer's information on file withAmazonwallet.com.

FIG. 4F illustrates the Amazon Wallet Account Access Page of theAmazonwallet.com web site 116, which is reached by customers 102 afterthe Login Page. This page allows Wallet customers 102 to view and updatethe Wallet account information by clicking on a button. The button leadsto an Update Page (not illustrated) that is similar in layout to the NewUser Page, but preferably has the information fields already filled in.The customer 102 can modify information as applicable and click anupdate button. The customer can also log out of Account Access byclicking on a Logout button. Another button allows a customer 102 toview a Wallet History Page.

FIG. 4G illustrates the Wallet History Page reached from the AccountAccess Page of the Amazonwallet.com web site 116. The History Page showsa list of when and to whom the customer's information has been provided.In the illustrated example, the History Page also lists the ordersplaced using the Amazon Wallet in terms of the associated merchants withwhom the orders were placed, the associated order numbers, and the timesthe orders were placed. These and other types of order history data maybe may be reported by the merchants to the information service on anorder-by-order, periodic, or other basis.

To assist the information service in creating an interests profile foreach customer (which may in turn be disseminated to the merchants), themerchants could be requested or required to report keywords thatdescribe the items purchased, and/or report “standard” productcategories in which the purchased items fall. The standard set of itemcategories may be published by the information service to the variousmerchants. The use of keywords and or standard categories would allowthe information service to build a customer profile without the need tomaintain a database of the items offered by the various merchants.

B. Implementation

FIG. 5 is a flowchart 500 illustrating a process through which customerinformation is provided to a merchant 104 in accordance with the firstspecific embodiment. The process illustrated in the flowchart 500assumes that the customer has already signed up with the informationservice 114. FIG. 6 illustrates a data flow diagram 600 showing thetransfer of information between the customer 102, the informationservice 114, and the merchant 104 in accordance with the first specificembodiment. The flowchart 500 will now be described in conjunction withthe data flow diagram 600.

Referring to the flowchart 500 of FIG. 5, the customer 102 browses atthe merchant web site 106 and identifies product(s) and/or service(s)for purchase at step 502, which is similar to step 222 of flowchart 220.The exchange of web pages and selections by the customer 102 andmerchant 104 is indicated by the two-way link 602 in the data flowdiagram 600, which is similar to the link 306 of the data flow diagram300. Step 502 brings the customer 102 to a Checkout Page such as, forexample, the one illustrated in FIG. 4B. At step 504, the merchant 104requests that the customer 102 provide her user ID and password, suchas, for example, is requested in the Checkout Page of FIG. 4B. Thetransmission of the request for the user ID and password is indicated bythe one-way link 604 from the merchant 104 to the customer 102 in thedata flow diagram 600. At step 506, the customer 102 provides her userID, and password, such as, for example, by filling out the form in theCheckout Page of FIG. 4B and clicking to make the purchase. Thesubmission of the user ID and password is indicated in the data flowdiagram 600 by the one-way link 606 from the customer 102 to themerchant 104. The request and submission of the customer's user ID andpassword as in steps 504-6 can be accomplished using well-knowntechniques such as HTML forms and Common Gateway Interface (CGI), aswell as SSL for security.

By sending her user ID and password to the merchant 104, the customer102 has authorized the merchant 104 to retrieve her customer informationfrom the information service 114. Accordingly, at step 508 the merchant104 sends the user ID and password to the information service 114 as isdepicted by the one-way link 608 from the merchant 104 to theinformation service 114 in the data flow diagram 600. The transmissionof the user ID and password can be performed over an insecurecommunications network 112 such as the Internet by using a securecommunications protocol. Alternatively, a secure direct link between themerchant 104 and the information service 114 could be established forcommunication between the information service 114 and the merchant 104.

At a next step 510, the information service 114 receives the informationrequest 608, containing the customer's user ID and password, from themerchant 102. At step 512, in order to help prevent fraud, theinformation service 114 authenticates the merchant 104 by checking itsdatabase 120 to determine whether the merchant 104 requesting theinformation is registered with the information service 114. At step 514the information service 114 authenticates the customer 104 by verifyingthat the submitted user ID and password match entries in the database120. If the user ID and password match, then at step 516, theinformation service 114 returns to the merchant 104 the customerinformation associated with the user ID and password. The one-way link616 in the data flow diagram 600 indicates the passing of the customerinformation to the merchant 104. In step 516, the customer informationis preferably communicated over the same communications link as was usedin step 508, but an alternate medium of communication could be used. Itwill be noted that steps 512 and 514 could be performed in an oppositeorder to that illustrated in the flowchart 500. Furthermore, step 512 isnot essential to the operation of the present embodiment and serves onlyas an extra security measure.

At step 518 the merchant 104 receives the customer information andprepares the transaction for confirmation by the customer 102 byreturning an order confirmation page to the customer 102. The orderconfirmation page could be, for example, the Order Confirmation Pageillustrated in FIG. 4C. The order confirmation page preferably includesa button for the customer 102 to click, such as is illustrated in theOrder Confirmation Page of FIG. 4C, to confirm her order. The orderconfirmation page may also be configured to allow a customer to modifythe information for completing the transaction. Optionally, the customerinformation may include several credit card numbers, several deliveryaddresses, and other information selectable by the customer at the timeof purchase. At the order confirmation page, the customer 102 could beprompted to select the appropriate information based upon which tocomplete the sale.

At a next step 520, the customer 102 confirms her order by clicking onthe “confirm order” button. At this point, the merchant 104 canoptionally display a Thank You page providing an order number, such asthe one illustrated in FIG. 4D.

Once the order has been confirmed by the customer 102, the merchant 104can use the credit card information included in the customer informationto initiate a charge. The merchant 104 can also use the shippinginformation to ship the order to the customer 102, if necessary. At anext step 522, the merchant 104 can optionally send order information,such as an order number, back to the information service 114 to bedisplayed on an order history page, such as the one illustrated in FIG.4G. The one-way link 622 in the data flow diagram 600 indicates thepassing of the order information to the information service 114. Asindicated above, the merchant may additionally or alternatively transferother types of information about the order, such as keywords andcategories of purchased items.

The merchant 104 may optionally create and account for the customerusing the user ID and password entered by the user and the informationobtained from the information service. In such implementations, themerchant and customer can subsequently transact business without theneed for addition transfers of the customer's information. The merchant104 may alternatively request the customer's information whenever thecustomer performs a transaction.

C. Alternative Implementations

In one alternative implementation of the present embodiment, theadditional element of security information, such as a mother's maidenname, is not used to protect the customer's account access to theinformation service 114. In order to maintain the security of thesystem, Amazon Wallet holders can be informed to use their wallet onlyat well known Internet merchants 104 the legitimacy of which need not bequestioned. For lesser-known Internet merchants, the information service114 can post a listing of legitimate participants or registrants to theAmazon Wallet program. Amazon Wallet holders can consult this site ifthey are unsure of whether a particular merchant 104 is legitimate.Accordingly, the possibility that an illegitimate entity will be able tosolicit user IDs and passwords is reduced.

The benefit of this alternative implementation is that many existingcustomer databases of Internet merchants may not include a secondelement of security information. By eliminating the use of the extraelement of security information, these databases could be directly usedto enable Amazon Wallet accounts for existing customers withoutadditional user interaction or additional solicitations of information.

In another alternative implementation, request for the user ID andpassword in step 506 could be implemented with forms that, althoughlocated on the merchant web site 106, are submitted directly to theinformation service 114. In this embodiment, step 508 can be omitted andthe merchant 104 does not see the customer's user ID or password.

IV. Second Specific Embodiment

In a second specific embodiment of the present invention, an Internetmerchant 104 displays a link to the information service web site 116,preferably from an order page. After the link is followed, theinformation service web site 116 displays a form requesting the entry ofa customer's user ID and password. Once the customer 102 submits heruser ID and password to the information service 114, the informationservice 114 returns to the merchant 104 the customer informationassociated with the user ID and password. The customer is then directedback to an order confirmation page on the merchant web site 106 toconfirm the sale. Once the customer 102 has confirmed the sale, themerchant 104 uses the customer information to process a payment and, ifapplicable, ship the order.

The primary distinction between the present embodiment and the previousembodiment is that the customer's user ID and password are submitteddirectly to the information service 114 rather than being passed throughthe merchant 104 to the information service 114. In accordance with thepresent embodiment, customers 102 are preferably informed only to submittheir user IDs and passwords directly to the information service. Sincecustomers 102 are informed only to submit their user ID and password tothe information service web site 116, illegitimate entities would bedeterred from setting up deceptive web sites to collect user IDs andpasswords. In this manner, the present embodiment is able to increasesecurity without requiring customers 102 to verify that individualmerchants 104 are registered with the information service 114. Thepresent embodiment also does not require an extra element of securityinformation for account access in order to achieve this increased levelof security. The present embodiment, therefore, could easily make use ofexisting customer databases that do not contain an extra element ofsecurity information. A further benefit is that user IDs and passwordsneed not be disclosed to the merchant 104. The user IDs and passwordsmay be valuable and confidential information that the informationservice 114 or customers 102 wish to maintain in secrecy.

In the first subsection below, a set of example web pages illustratesthe present embodiment from the perspective of the customer 102. In anext subsection, a flowchart and data flow diagram illustrate thepresent embodiment from an implementation perspective.

A. Example Web Pages

FIGS. 7A-E illustrate a number of example web pages that are displayedto a customer 102 in accordance with the second specific embodiment ofthe present invention. Reference is also made back to some of FIGS. 4A-Gsince certain example pages are the same or similar. The illustratedexample also uses the hypothetical Merchant.com, Amazonwallet.com, andAmazon Wallet terms introduced in the first specific embodiment above.

FIG. 7A illustrates an Amazon Wallet New User Page of theAmazonwallet.com web site 116. The page is similar to the page of FIG.4A, however, the field requesting the mother's maiden name and theaccompanying security note are omitted. In place of the security note ispreferably a security note warning customers that they should onlysubmit their user ID and password to the Amazonwallet.com web site. Oncea new customer 102 fills in the new user information and submits theform, the customer 102 can then use the wallet to shop at the web sitesof Internet merchants that have registered with the information service114.

If the customer 102 is already an existing customer of Amazon.com, whichpreferably operates Amazonwallet.com, the process of filling in the newuser information may be bypassed. In this case, the customer informationalready on file with Amazon.com could be used to make the Amazon Walletautomatically active.

FIG. 7B illustrates a Checkout Page that a customer 102 reaches at theMerchant.com web site 106 after selecting one or more products and/orservices for purchase. The Checkout Page lists the order and presents tothe customer 102 a button to use the Amazon Wallet for entry of paymentand/or shipping information. If the customer 102 chooses to use theAmazon Wallet, the customer 102 clicks on the associated button and isdirected to the Amazon Wallet Authentication Page.

FIG. 4C illustrates the Amazon Wallet Authentication Page of theAmazonwallet.com web site 116. The page requests the user ID andpassword of the customer 102. The page provides a button for accountaccess. The page also provides a button that can be clicked to send thecustomer information to the referring merchant 102. Assuming that thelatter button is clicked, the customer information is transferred to thereferring merchant and the customer's web browser 109 is then directedback to the merchant's web site.

FIG. 7D illustrates an Order Confirmation Page of the Merchant.com website 106 that is displayed to the Amazon Wallet customer 102 afterreturning from the Amazon Wallet Authentication Page. The page againlists the order, the name of the customer 102 in order to confirm theidentity of the customer, the shipping address, and the last severaldigits of the credit card being charged. The additional information suchas the customer's shipping address can be safely displayed here sinceAmazonWallet.com has authenticated the customer and there is a low riskthat the user ID and password have been compromised. The page alsodisplays a “confirm order” button. After selecting the “confirm order”button, the Amazon Wallet customer next sees a Thank You page of thetype illustrated in FIG. 4D. The page confirms that the order has beenplaced, provides an order number for order tracking, and thanks thecustomer 102.

FIG. 7E illustrates an Amazon Wallet Account Access Page of theAmazonwallet.com web site 116 that is reached by customers 102 byselecting the account access button from the Amazon WalletAuthentication Page of FIG. 7C. This page of the Amazonwallet.com website allows Wallet customers 102 to view and update their Wallet accountinformation in a manner similar to the first specific embodiment. Anoptional link can be displayed if the customer entered the AccountAccess Page after being referred by a merchant to the AmazonWallet.comweb site. The optional link allows the customer 102 to submit hercustomer information to the referring merchant and log out of AccountAccess simultaneously. The customer can also log out of Account Accessby clicking on a Logout button. Another button allows a customer 102 toview a History Page that is similar to that illustrated in FIG. 4G. Asin the first specific embodiment, the history page can also display alisting of the purchases made using the Amazon Wallet.

B. Implementation

FIG. 8 is a flowchart 800 illustrating a process through which customerinformation is provided to a merchant 104 in accordance with the secondspecific embodiment. The process illustrated in the flowchart 800assumes that the customer has already signed up with the informationservice 114. FIG. 9 illustrates a data flow diagram 900 showing thetransfer of information between the customer 102, the informationservice 114, and the merchant 104 in accordance with the second specificembodiment. The flowchart 800 will now be described in conjunction withthe data flow diagram 900.

Referring to the flowchart 800 of FIG. 8, the customer 102 browses atthe merchant web site 106 and identifies product(s) and/or service(s)for purchase at step 802, which is similar to step 502 of flowchart 500.The exchange of web pages and selections by the customer 102 andmerchant 104 is indicated by the two-way link 902 in the data flowdiagram 900, which is similar to the link 602 of the data flow diagram600. At step 804, the merchant 104 returns to the customer 102 aCheckout Page such as, for example, the one illustrated in FIG. 7B. TheCheckout Page displays a link to the information service web site 116allowing the customer 102 to use the information service 114 to providepayment information. The transfer of the Checkout Page containing thelink to the information service web site 116 is indicated by the one-waylink 904 in the data flow diagram 900. At step 806, the customer 102,choosing to use the information service 114, follows the link to theinformation service web site 116.

In one implementation of the present embodiment, the link to theinformation service web site 116 provided in step 804 can be configured,using the well-known techniques of URL encoding and CGI (Common GatewayInterface), to transfer information to the information service server118. Using URL encoding, the merchant appends a code identifying itselfand an identifying order number to the link to the information serviceweb site 116. Additionally, the merchant could encode other information,such as, for example, item numbers, prices, etc. in the link to theinformation service web site 116. When the link is followed the appendedinformation is submitted to a CGI program or script on the informationservice server 118. The CGI program on the information service server118 can then identify the merchant and an identifying order number.

At step 808, the CGI program returns to the customer 102 a request forthe customer's user ID and password. The request is preferablyimplemented using a form such as, for example, the one illustrated inFIG. 7C. The transmission of the request for the user ID and password isindicated by the one-way link 908 from the information service 114 tothe customer 102 in the data flow diagram 900. At step 810, the customer102 provides her user ID and password and submits the form to anotherCGI program located on the information service server 118. Thesubmission of the user ID and password is indicated in the data flowdiagram 900 by the one-way link 910 from the customer 102 to theinformation service 114. The request and submission of the customer'suser ID and password as in steps 808-810 can be accomplished usingwell-known techniques such as HTML forms and Common Gateway Interface(CGI), as well as SSL for security.

At step 812, the CGI program authenticates the customer by checking thatthe submitted user ID and password combination is present in theinformation service database 120. At step 814, if the authenticity ofthe customer 102 is verified, the CGI program sends the customerinformation associated with the user ID to the merchant 104. Theinformation server 118 preferably appends to the customer informationthe identifying order number that was originally provided by themerchant 104. The identifying order number allows the merchant 104 toassociate the customer information received with a pending order. Thetransmission of the customer information from the information service114 to the merchant 104 is indicated by the one-way link 914 in the dataflow diagram 900. The customer information can be sent in any number ofways, such as, for example, using URL encoding, CGI, and SSL over theInternet. Alternatively, the information could be transferred over adirect link between the information service 114 and the merchant 104.There are also numerous other well-known protocols and methods thatcould be used to securely transfer the information.

At a next step 816, the merchant 104 receives the customer informationand the associated order number. The merchant 104 then processes thecustomer information and returns, to the information service 114, a linkor uniform resource locator (URL) to a new order confirmation page. Thetransfer of the URL from the merchant 104 to the information service 114is indicated by the one-way link 916 in the data flow diagram 900. At anext step 818 the information service 114 receives the link to the orderconfirmation page and redirects the customer 102 to the page. Thepassing of the URL of the page to which the customer 102 is redirectedis indicated by the one-way link 918 from the information service 114 tothe customer 102 in the data flow diagram 900.

From the perspective of the customer 102, all of steps 812-816 appear asone step in which the customer submits her user ID and password and isthen brought to the order confirmation page, such as, for example, thepage illustrated in FIG. 7D. The order confirmation page preferablyincludes a button for the customer 102 to click to confirm her order.The order confirmation page may also be configured to allow a customerto modify the information based upon which the sale will be completed.Optionally, the customer information may include several credit cardnumbers, delivery addresses, etc. that are selectable by the customer atthe time of purchase.

At step 820, the customer 102 confirms the order by clicking on the“confirm order” button. At this point, the merchant 104 can optionallydisplay a Thank You page providing an order number, such as the oneillustrated in FIG. 4D of the first specific embodiment.

Once the order has been confirmed by the customer 102, the merchant 104can use the credit card information included in the customer informationto initiate a charge against the customer's credit card. The merchant104 can also use the shipping information to ship the order to thecustomer 102, if necessary. At step 822, the merchant 104 can optionallysend order information, such as an order number, back to the informationservice 114 to be displayed on an order history page, such as the oneillustrated in FIG. 4G of the first specific embodiment. The one-waylink 922 in the data flow diagram 900 indicates the passing of the orderinformation to the information service 114. As indicated above, theorder information, which may include item keywords and categories, maybe aggregated by the information service and used to generate anddisseminate customer profiles.

V. Third Specific Embodiment

In a third specific embodiment of the present invention, an Internetmerchant 104 displays a button on an item detail or other page thatallows a customer 102 to purchase an item with a single mouse clickwithout ever having provided information to or registered with themerchant 104. In response to the single mouse click, the informationservice 114 provides the customer information and an identification ofthe desired product to the merchant 104. The customer 102 enables thissingle click feature, after registering with the information service114, by submitting her user ID and password to the information service114 for authentication.

The use of a single mouse click or other action to make a purchase froma merchant is described in U.S. Pat. No. 5,960,411. The presentembodiment extends the use of the single-click concept to function withmerchants with whom the customer has no previous establishedrelationship. Like the presently implemented 1-Click system, the presentembodiment is preferably configured to consolidate all purchases from asingle merchant 104 using a single-click service within a time period,such as 90 minutes, into a single order. Alternatively, othersingle-click order consolidation schemes could be used.

In the first subsection below, a set of example web pages illustratesthe present embodiment from the perspective of the customer 102. In anext subsection, a flowchart and data flow diagram illustrate thepresent embodiment from an implementation perspective. In a thirdsubsection, a number of alternative implementations of this embodimentare disclosed.

A. Example Web Pages

FIGS. 10A-E illustrate a number of example web pages that are displayedto a customer 102 in accordance with the third specific embodiment ofthe present invention. Reference is also made back to some of FIGS. 7A-Esince certain example pages are the same or similar. In the illustratedexample, Merchant.com, a hypothetical merchant, serves as the Internetmerchant 104, and Amazon1-click.com serves as the hypotheticalinformation service 114. In the context of these web pages, “1-Click”represents the name of the service provided by the present embodimentthat a customer 102 uses to make purchases using only a single mouseclick from Internet merchants with which the customer may have noprevious existing relationship.

Referring back to FIG. 7A, a New User Page similar to that illustratedfor the second specific embodiment could also be used to registercustomers for the third specific embodiment. The 1-Click New User Pageis located on the Amazon1-click.com web site 116. The security notewarning customers that they should only submit their user ID andpassword to, in this case, the Amazon1-click.com web site, is preferablyretained. Once a new customer 102 fills in the new user information andsubmits the form, the customer 102 can then activate the 1-Click featureto shop at the web sites of Internet merchants that have registered withthe information service 114.

If the customer 102 is already an existing customer of Amazon.com, whichoperates Amazon1-click.com in this example, the process of filling inthe new user information may be bypassed. In this case, the customerinformation already on file with Amazon.com could be used to make theAmazon Wallet automatically active.

FIG. 10A illustrates a Login to Account Access Page located on theAmazon1-click.com web site 116. This page serves as a gateway to thecustomer's access to her own customer information and 1-Click settings.An additional button can be displayed on this page allowing a customerto turn the 1-Click service off if it is presently turned on.

FIG. 10B illustrates a 1-Click Account Access Page, located on theAmazon1-click.com web site 116, that is reached from the Login page ofFIG. 10A. One button on the page allows a customer 102 to activate the1-Click feature. The page also allows 1-Click customers 102 to view andupdate the 1-Click account information by clicking on an Update button.The Update button leads to an Update Page (not illustrated) that issimilar in layout to the New User Page, but preferably has theinformation fields already filled in. An Order History button allows acustomer 102 to view an Order History Page that will be discussed below.The customer can also log out of Account Access by clicking on a Logoutbutton.

FIG. 10C illustrates an Item Detail Page that is displayed on theMerchant.com web site 106 if the customer 102 has activated the 1-Clickfeature. A 1-Click purchase graphic 1010, allowing the customer 102 topurchase the displayed product using the 1-Click feature, is displayedwith the name of the customer 102. By clicking on the 1-Click graphic1010, an order is automatically generated and the customer's informationis automatically retrieved from the information service 114 with nofurther action on the part of the customer 102. Preferably, after awaiting time, such as 90 minutes, the customer 102 is charged and (ifapplicable) shipment is initiated. The waiting time gives the customeran additional opportunity to make additional purchases using the 1-Clickfeature and have the additional purchases consolidated into a singleorder and possibly shipped together. Another button titled “Add Item toshopping cart” gives the customer 102 the option of adding the displayeditem to a shopping cart in order to make a purchase using conventionalmethods.

FIG. 10D illustrates a 1-Click Order History Page that can be accessedby a customer on the Amazon1-click.com web site 116 from the AccountAccess Page. The Order History page displays a listing, for eachmerchant 104, of the pending and placed orders using the 1-Clickservice. Pending orders are those for which the waiting time has notexpired. Associated with each merchant 104 is a link or button thattakes the customer 102 to an Order History and Review Page for therespective merchant 104.

FIG. 10E illustrates the Order History and Review Page located on theMerchant.com web site 106. The page displays a history of placed ordersand some information relating to the orders. The page also displays anypending orders and gives the customer 102 the option of changing thequantities of the products in the pending order. The time remainingbefore the pending order will be placed may also be displayed.

B. Implementation

FIGS. 11A-B are a flowchart 1100 illustrating a process through whichcustomer information is provided to a merchant 104 in accordance withthe third specific embodiment. The process illustrated in the flowchart1100 assumes that the customer has already signed up with theinformation service 114. FIG. 12 illustrates a data flow diagram 1200showing the transfer of information between the customer 102, theinformation service 114, and the merchant 104 in accordance with thethird specific embodiment. The flowchart 1100 will now be described inconjunction with the data flow diagram 1200 of FIG. 12.

Referring now to the flowchart 1100, at step 1102, the informationservice server 118, in response to the customer 102 accessing theinformation service web site 116, requests the customer's user ID andpassword. The request is preferably implemented using a form such as,for example, the one illustrated in FIG. 10A. The transmission of therequest for the user ID and password is indicated by the one-way link1202 from the information service 114 to the customer 102 in the dataflow diagram 1200. At step 1104, the customer 102 provides her user IDand password and submits the form to a CGI program located on theinformation service server 118. The submission of the user ID andpassword is indicated in the data flow diagram 1200 by the one-way link1204 from the customer 102 to the information service 114. The requestand submission of the customer's user ID and password as in steps1102-1104 can be accomplished using well-known techniques such as HTMLforms and Common Gateway Interface (CGI), as well as SSL for security.

At step 1106, the CGI program authenticates the customer by checkingthat the submitted user ID and password combination is present in theinformation service database 120. If the authenticity of the customer102 is verified, the CGI program directs the customer's web browser 109to an account access page such as the one illustrated in FIG. 10B. Theaccount access page allows the customer 102 to activate the single clickfeature by clicking on a button. At step 1108, if the customer 102chooses to activate the single click feature, the information serviceserver 118 returns to the customer 102 a new web page (not illustratedby example in the figures) informing the customer 102 that the singleclick feature has been activated. In returning the new web page, server118 places a cookie on the customer's computer 110. The cookie containsinformation identifying the customer 102 and indicating that thecustomer 102 has activated the single click feature. The transfer of thecookie is indicated in the data flow diagram 1200 by the one-way link1208 from the information service 114 to the customer 102.

The use and characteristics of cookies in conjunction with web browsersare well known in the art and will not be discussed in detail herein.One important characteristic of cookies, however, should be kept inmind. Each cookie has a parameter, called its domain, that specifies thevalid domain of the cookie. Whenever a link is followed to a web serverwith a domain name within the cookie's domain, the information in thecookie is also passed along to the server. Furthermore, in placing acookie on a customer's computer 110, a server may only assign to it adomain to which the server belongs. Accordingly, in the presentembodiment, the cookie placed on the customer's computer 110 by theinformation service server 118 is only returned to servers with the samedomain name as the information service server 118. As a consequence, thecookie identifying the customer 102 and signifying that the customer hasenabled the single click feature will not be passed on to merchantservers 108 having different domain names than the information serviceserver 118. Although the cookie will not be submitted to the merchantserver 108, the merchant server can display a web page with a link tothe information service server 118. This link, in turn, will cause thecookie to be submitted to the information service server.

Once the customer 102 has activated the single click feature, thecustomer 102 browses a merchant web site 106 at step 1110. At step 1112,the merchant 104 displays an item detail page on the customer's webbrowser 109, such as for example, the page in FIG. 10C. The item detailpage identifies the item and provides a single click purchase graphic1010 (FIG. 10C) for which the image is retrieved from the informationservice server 118. The transfer of the item detail page is indicated bythe one-way link 1212 from the merchant 104 to the customer 102 in thedata flow diagram 1200.

At step 1114, when the customer's web browser 109 encounters the URL ofthe graphic 1010, the browser 109 automatically generates an HTTPrequest to retrieve the graphic 1010 from the information service server118. Since the domain name of the information service server 118 iswithin the domain of the cookie placed on the customer's computer 110,the cookie is also sent in conjunction with the request. Thetransmission of the cookie with the request for the graphic 1010 isindicated by the one way link 1214 from the customer 102 to theinformation service 114 in the data flow diagram 1200.

At step 1116, a CGI program on the information service server 118receives the HTTP request for the graphic 1010 from the customer's webbrowser 109. If the customer 102 has activated the single click feature,the CGI program retrieves the customer information associated with thecookie that was sent along with the request. At a next step 1118, theCGI program responds to the web browser's request for the graphic 1010with an image that is displayed by the customer's web browser 109. Asdepicted in FIG. 10C, the image is preferably in form of a box thatidentifies the customer and gives the customer 102 the option ofclicking on a button to purchase the featured item. The transfer of theimage is represented by the one-way link 1218 from the informationservice 114 to the customer 102 in the data flow diagram 1200.

Returning to step 1116, if the customer 102 has not activated the singleclick feature, no cookie is sent to the CGI program processing therequest on the information service server 118. In this case the CGIprogram can respond to the HTTP request for the graphic with an imageoffering the customer 102 the opportunity to activate or sign up withthe single click service. Alternatively, during a previous step, theinformation service 114 could have placed a cookie on the customer'scomputer 110 indicating that the customer 102 has signed up for theservice but has not activated it. In this case the CGI program candisplay the appropriate image offering the customer 102 the opportunityto either sign up for or activate the single click feature asapplicable.

At a next step 1120, a customer 102 who has activated the single clickfeature clicks on the single click purchase graphic 1010 downloaded fromthe information service server 118. The associated with the graphic 1010is a link that is also serviced by the information service server 118through another CGI program. Therefore, at step 1122, the customer's webbrowser 109 again submits the cookie to the information service server118. The link associated with the graphic 1010 also has appended to it,preferably using URL encoding, a merchant identifier by which theinformation service 114 can identify the merchant 104, as well as aproduct identifier by which the merchant 104 can identify the selectedproduct. In sum, by clicking on the graphic 1010 and following the linkto the information service server 118, the customer 102 provides thecookie identifying the customer 102 as well as the identity of thedesired product and the identity of the associated merchant, which areencoded within the URL of the link associated with the graph 1010. Thecustomer's clicking on the graphic 1010 generates another HTTP requestthat is indicated by the one-way link 1120 from the customer 102 to theinformation service 114 in the data flow diagram 1200.

At step 1124 the CGI program on the information service server 118processes the HTTP request resulting from the click on the single clickpurchase graphic 1010. The CGI program compiles the customer informationassociated with the cookie from the database 120, appends the product IDthat was URL encoded with the URL associated with the graphic 1010, andsends the information to the merchant 104. The communication of theinformation from the information service 114 to the merchant 104 isindicated by the one-way link 1224 in the data flow diagram 1200. Thiscommunication can be effectuated through any of the methods suggested inconjunction with the first and second specific embodiments above. Inresponse to the HTTP request resulting from the customer's selection ofthe graphic 1010, the information service server 118 can return to thecustomer 102 a thank you page (not illustrated) confirming that thesingle click purchase has been processed.

At a next step 1126, the merchant 104 receives the customer informationand product ID. At step 1128, the merchant 104 creates an order for theidentified product using the customer information. If an order from thesame customer 102 is already pending, the merchant 104 can add theidentified product to the pending order. Once the merchant 104 placesthe order, it can send a message back to the information service 114indicating that the order has been placed.

In subsequent steps not illustrated in the flowchart 1100, the customer102 can log in to the information service web site 116, access her orderhistory page, and follow a link to the merchant's order history andreview page. At the merchant's order history and review page, thecustomer can modify or cancel any pending order and view placed orders.

C. Alternative Implementations

In one alternative implementation of this third specific embodiment, theinformation service 114 could send the customer's user ID along with thecustomer information to merchant 104 so that merchant 104 can easilyconsolidate 1-Click orders without attempting to match customerinformation.

In another implementation, the graphic 1010 could include a text entrybox in which the customer 102 supplies a password. The password is sentalong with the HTTP request 1120 to the information service and can beused as an extra element of security in authenticating the customer 102.

In another alternative implementation, the information service server118 could direct the customer 102 to an order history and review page onthe merchant's web site 106 after the customer clicks on the singleclick purchase graphic 1010. This feature could be implemented byredirecting the customer's web browser 109 back to the merchant web site106 after the information service server 118 receives a response from asingle click link. Sufficient information could be appended to theredirect URL using URL encoding to allow the merchant server 108 toidentify the customer 102 and display the appropriate web page.

In still another alternative implementation, the merchant 104 could alsodeposit a cookie on the customer's computer 110. The merchant 104 couldthen use the cookie to allow the customer 102 to check an order historyand review page without first logging into the information service 114.The cookie could also be used to provide a separate single click featurethat does not require interaction with the information service 114.

In other implementations, the features of the present embodiment couldbe implemented using more comprehensive web tools such as Java andframes. These other implementations could provide additional features.For example, using frames, the single click graphic 1010 could bereplaced with a frame. The Java programming language could also be usedin conjunction with the frame to provide some interactive and/orprocessing capabilities to the single click purchase frame.

VI. Alternative Embodiments

In an alternative embodiment, any of the above embodiments could bemodified to combine the user ID and password into a passcode. In anotheralternative embodiment, the information service 114, instead of thecustomer 102, could select and/or provide the user ID and/or password.In other embodiments, other forms of authentication, such as a key fileor a talbage-response method, could replace the use of the user ID andpasscode.

In further embodiments, the information service 114 could provide thecustomer's user ID and password to the merchant 104 in conjunction withproviding the customer information. With this information, the merchant104 could allow the customer 102 to login directly to the merchant website 106, access account information and make purchases using herexisting information service 114 user ID and password.

In an additional embodiment, the information service 114 can act as apayment intermediary in addition to providing customer information. Inaccordance with this embodiment, the information service 114 can chargethe customer 102 and in turn the information service 114 can makepayment to the merchant 104. The information service 114 can charge acommission to the customer 102 and/or the merchant 104 for using thepayment intermediary service. The payment intermediary service can becombined with the information intermediary service such that theinformation service 114 provides customer information as well as servingas a payment intermediary. Alternatively, the information service 114could act as a payment intermediary instead of providing customerinformation.

In still other alternative embodiments, various features of theabove-described embodiments could be combined to provide otherconveniences to the Internet shopper.

Although the invention has been described in terms of certain preferredembodiments, other embodiments that are apparent to those of ordinaryskill in the art, including embodiments which do not provide all of thefeatures and advantages set forth herein, are also within the scope ofthis invention. Accordingly, the scope of the invention is defined bythe claims that follow. In the method claims, reference characters areused for convenience of description only, and do not indicate aparticular order for performing the method.

What is claimed is:
 1. A system, comprising: a first server system thatoperates in a first network domain, said first server system storingaccount information, including payment information, of a user, saidfirst server system providing a service for enabling users to placeorders on merchant sites without having to create accounts with suchmerchant sites; and a second server system that operates in a secondnetwork domain that is distinct from the first network domain, saidsecond server system hosting a merchant site of a merchant, saidmerchant site including a page that includes a reference to a displayobject served by the first server system, said reference configured tocause browsers that load the page from the second server system torequest the display object from the first server system for display onthe page; said first server system operative to transmit, to a usercomputing device of the user, a browser cookie for storage on the usercomputing device, said browser cookie corresponding to the first networkdomain but not the second network domain, said browser cookie includinginformation that enables the first server system to associate thebrowser cookie with the user; said first server system configured torespond to a browser request from the user computing device for thedisplay object by at least (1) personalizing the display object withinformation associated with the user, said information associated withthe user retrieved by the first server system using the browser cookieas received from the user computing device, and (2) transmitting thepersonalized display object to the user computing device for display onthe page of the merchant site, said personalized display objectproviding functionality for the user to use the service to place anorder on the merchant site.
 2. The system of claim 1, wherein thedisplay object includes a field for user entry of a password forauthenticating with the service.
 3. The system of claim 1, wherein thedisplay object is configured for display as a frame on said page.
 4. Thesystem of claim 1, wherein the display object is configured for displayas a box on said page.
 5. The system of claim 1, wherein the page is anitem detail page corresponding to an item that is available for purchasefrom the merchant site, and the display object provides functionalityfor the user to use said service to place an order for the item from themerchant site.
 6. The system of claim 1, wherein the display object is asingle-action object that enables the user to place an order with asingle selection action.
 7. The system of claim 1, wherein the firstserver system is configured to use the payment information of the userto initiate collection of payment for the order on behalf of themerchant.
 8. The system of claim 1, wherein the first server system isconfigured to transmit shipping information of the user to the secondserver system in connection with said order.
 9. The system of claim 1,wherein the information associated with the user comprises a name of theuser.
 10. The system of claim 1, wherein the first server systemprovides functionality for the user to log into the service and view ahistory of purchase transactions performed by the user across aplurality of merchant sites.
 11. A system, comprising: a server thatoperates in a first network domain, said server programmed to provide apayment service that enables users to perform payment transactions onmerchant sites, including a merchant site hosted in a second networkdomain that is distinct from the first network domain; and a databasecoupled to the server, said database storing account information,including payment information, of users registered with the paymentservice; said server programmed to implement a process that comprises:transmitting a browser cookie associated with the service to a usercomputing device for storage thereon, said browser cookie correspondingto the first network domain but not the second network domain;subsequently receiving, from the user computing device, said browsercookie and a request for a display object to display on a page of themerchant site; and responding to the request by transmitting to the usercomputing device, for display on the page of the merchant site, apersonalized display object that includes user information associatedwith the browser cookie, said personalized display object providingfunctionality for the user to use the payment service to place an orderon the merchant site.
 12. The system of claim 11, wherein thepersonalized display object includes a text entry box for user entry ofa password for authenticating with the payment service.
 13. The systemof claim 11, wherein the personalized display object is configured fordisplay as a box on said page.
 14. The system of claim 11, wherein thepersonalized display object is configured for display as a frame on saidpage.
 15. The system of claim 11, wherein the personalized displayobject is a single-action purchase object that enables the user toauthorize a purchase transaction with a single selection action.
 16. Thesystem of claim 11, wherein the user information associated with thebrowser cookie includes a name of the user.
 17. The system of claim 11,wherein the server is configured to send shipping information of theuser to the merchant site in connection with the order.
 18. The systemof claim 11, wherein the server is configured to initiate collection ofa payment from the user for said order on behalf of the merchant site.19. A method comprising: receiving, from a user computing device, a useridentifier and a request for a display object to display on a page of amerchant site, wherein the merchant site is hosted on a first server ina first network domain, wherein the request is generated by the usercomputing device based on a reference included in said page, wherein theuser identifier is stored on the user computing device of a user and theuser identifier corresponds to a second network domain, and wherein thesecond network domain has associated therewith a database storing useraccount information, including payment information, and the secondnetwork domain is distinct from the first network domain; and respondingto the request for the display object by generating, and transmitting tothe user computing device, a personalized display object for display onthe page of the merchant site, said personalized display objectproviding functionality for the user to use the user account informationto place an order with the merchant site without registering with themerchant site, wherein generating the personalized display objectcomprises using the received user identifier to retrieve informationassociated with the user from said database.
 20. The method of claim 19,wherein the user identifier is a browser cookie.
 21. The method of claim20, wherein the display object includes a field for user entry of apassword for authenticating with the second network domain.
 22. Themethod of claim 19, wherein the method is performed in its entirety by asecond server that operates in the second network domain.
 23. The methodof claim 22, wherein the display object includes a field for user entryof a password for authenticating with the second server.
 24. The methodof claim 19, wherein the personalized display object is personalizedwith a name of the user.
 25. The method of claim 19, wherein thepersonalized display object is configured for display as a box on saidpage.
 26. The method of claim 19, wherein the personalized displayobject is configured for display as a frame on said page.